Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

I just tried to run tests locally and I see number of tests failing the build with aot and trimming analyzer errors. Do you have a local fix for it that you plan to PR?

I just tried to run tests locally and I see number of tests failing the build with aot and trimming analyzer errors. Do you have a local fix for it that you plan to PR?

I don't see those errors locally (I just did a test run a couple hours ago).

Or do we also WarnAsError for test build now? (I do have the "please don't waste my time" environment variable set on all my machines so the warnings don't fail the build for me.)

Yes, WarnAsError is enabled for parts of the test build now. I am seeing errors like:

C:\runtime\artifacts\tests\coreclr\obj\windows.x64.Checked\Managed\JIT\HardwareIntrinsics\General\Vector128_1\Vector128
_1_r\Vector128_1_r\gen\AsVector.Int32.cs(76,39): error IL2060: Call to 'System.Reflection.MethodInfo.MakeGenericMethod(
params Type[])' can not be statically analyzed. It's not possible to guarantee the availability of requirements of the
generic method. [C:\runtime\src\tests\JIT\HardwareIntrinsics\General\Vector128_1\Vector128_1_r.csproj] [C:\runtime\src\
tests\build.proj]

#88209